deploy <jboss-install>/docs/teiid/examples/dynamicvdb-portfolio/portfolio-vdb.xml
Having built the VDB or using the example dynamic vdb, it must be deployed into the JBoss AS server so it can be accessed using a Teiid JDBC connection.
This example is using the dynamic vdb and requires that it be deployed into the JBoss AS server. There are different ways to deploy a VDB file into JBoss AS 7.1. Below is one simple method works by copying the VDB file to certain location under the JBoss AS 7.1.
Copy the "<jboss-install>/docs/teiid/examples/dynamicvdb-portfolio/portfolio-vdb.xml" following file into "<jboss-install>/standalone/deployments" directory:
Create a marker file (just an empty file) in the same directory as where the VDB file is copied, with same name as VDB file name with ".dodeploy" as extension. For example, for above VDB file create "portfolio-vdb.xml.dodeploy"
Then the JBoss AS 7.1 directory scanner will find this file and deploy the VDB file.
CLI based deployment is another simple way to deploy variety of artifacts into JBoss AS 7.1. Execute "jboss-admin.sh" in the "<jboss-install>/bin" and connect to the running JBoss AS instance. Then issue following command
deploy <jboss-install>/docs/teiid/examples/dynamicvdb-portfolio/portfolio-vdb.xml
If the data sources are created correctly and VDB deployed correctly, then you will see an informational message in the JBoss AS 7.1 console that the VDB has been deployed and in "active" state. If there are any errors then you will see the VDB not deployed or in "inactive" state. Find the issues on the console and fix them before you proceed any further.
If you seen VDB in "active" state, then go to the next section to learn how to connect to the VDB.